SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 49159: The SAS® Pooled Workspace Server stops responding when internal accounts that contain a comma in the name are used to make requests

DetailsAboutRate It

The SAS Pooled Workspace Server becomes unresponsive when a SAS internal account that contains a comma in its name is used to request connections. When this situation occurs, the port that is used by the SAS Pooled Workspace server process to listen for the incoming client is not returned to the SAS® Object Spawner's port bank. Requests to the SAS Pooled Workspace server will not be successful after all ports in the SAS Object Spawner port bank are depleted. There are three ports in the port bank by default.

To correct this problem, refresh the SAS Object Spawner. To avoid this problem in the future, do not create SAS internal accounts that contain a comma in the name.

Tips

From "Chapter 2: User Administration Tasks" in SAS® 9.3 Management Console: Guide to Users and Permissions (page 17):

"Tip: We recommend that you avoid using spaces or special characters in the name of a user, group, or role that you create. Not all components support spaces and special characters in identity names."

From "Chapter 10: Authentication Mechanisms" in SAS® 9.3 Intelligence Platform: Security Administration Guide (page 118):

Tip: "Internal accounts aren't intended for regular users (they are intended for only SAS Metadata administrators and some service identities)."


Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemN/ATru64 UNIX9.2 TS2M39.4 TS1M0
Solaris for x649.2 TS2M39.4 TS1M0
OpenVMS on HP Integrity9.2 TS2M39.4 TS1M0
Linux on Itanium9.2 TS2M39.4 TS1M0
Linux for x649.2 TS2M39.4 TS1M0
Linux9.2 TS2M39.4 TS1M0
HP-UX IPF9.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 Enterprise Edition9.2 TS2M39.4 TS1M0
z/OS9.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 for x649.2 TS2M39.4 TS1M0
Microsoft Windows Server 2008 for x649.2 TS2M39.4 TS1M0
Microsoft® Windows® for 64-Bit Itanium-based Systems9.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.2 TS2M39.4 TS1M0
Microsoft Windows XP 64-bit Edition9.2 TS2M39.4 TS1M0
HP-UX9.2 TS2M39.4 TS1M0
64-bit Enabled Solaris9.2 TS2M39.4 TS1M0
64-bit Enabled HP-UX9.2 TS2M39.4 TS1M0
64-bit Enabled AIX9.2 TS2M39.4 TS1M0
Windows Vista for x649.2 TS2M39.4 TS1M0
Windows Vista9.2 TS2M39.4 TS1M0
Windows 7 Ultimate x649.2 TS2M39.4 TS1M0
Windows 7 Ultimate 32 bit9.2 TS2M39.4 TS1M0
Windows 7 Professional x649.2 TS2M39.4 TS1M0
Windows 7 Professional 32 bit9.2 TS2M39.4 TS1M0
Windows 7 Home Premium x649.2 TS2M39.4 TS1M0
Windows 7 Home Premium 32 bit9.2 TS2M39.4 TS1M0
Windows 7 Enterprise x649.2 TS2M39.4 TS1M0
Windows 7 Enterprise 32 bit9.2 TS2M39.4 TS1M0
Microsoft Windows XP Professional9.2 TS2M39.4 TS1M0
Microsoft Windows Server 20089.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 Standard Edition9.2 TS2M39.4 TS1M0
Microsoft® Windows® for x649.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 Datacenter Edition9.2 TS2M39.4 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.